Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: abf2d15c2af125285389c97a33861f61b0eedde5cf7e7657d047ab39577700e4

Tx prefix hash: 4287ee24811ac1b6da29570ea5f815566fd7af223fd2d5784e3b19daf79a15dd
Tx public key: 56c35820be532aa94ce6b64e1a5b31241458c9caf7be6fbc95f1254bd45b193d
Timestamp: 1702267516 Timestamp [UCT]: 2023-12-11 04:05:16 Age [y:d:h:m:s]: 01:048:13:04:37
Block: 910540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295833 RingCT/type: yes/0
Extra: 0156c35820be532aa94ce6b64e1a5b31241458c9caf7be6fbc95f1254bd45b193d02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37aacfac9c66bbd91cb9e5aa837317f442606562a52bc33a5789a4c683818bcc 0.600000000000 1367701 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 910550, "vin": [ { "gen": { "height": 910540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37aacfac9c66bbd91cb9e5aa837317f442606562a52bc33a5789a4c683818bcc" } } ], "extra": [ 1, 86, 195, 88, 32, 190, 83, 42, 169, 76, 230, 182, 78, 26, 91, 49, 36, 20, 88, 201, 202, 247, 190, 111, 188, 149, 241, 37, 75, 212, 91, 25, 61, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8