Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dfc4c3049b7deeebbae116988b0964bebee54f63d4b3c4e38e77cf7b3dffb3c

Tx prefix hash: e72565f5c98b97c26c49318fc930dc902bd2e8309c337cbaece534935598331b
Tx public key: 73d7d3df3bdbc4a505811676c80450a97f3ee81e08ccb2079d706cafa5f05c67
Timestamp: 1737084369 Timestamp [UCT]: 2025-01-17 03:26:09 Age [y:d:h:m:s]: 00:330:11:12:56
Block: 1199039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233737 RingCT/type: yes/0
Extra: 0173d7d3df3bdbc4a505811676c80450a97f3ee81e08ccb2079d706cafa5f05c67021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a61db52216964236f8eb5bc3b8f003683c86bc7523133b5f669a25782a9ac2e 0.600000000000 1685668 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": 1199049, "vin": [ { "gen": { "height": 1199039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a61db52216964236f8eb5bc3b8f003683c86bc7523133b5f669a25782a9ac2e" } } ], "extra": [ 1, 115, 215, 211, 223, 59, 219, 196, 165, 5, 129, 22, 118, 200, 4, 80, 169, 127, 62, 232, 30, 8, 204, 178, 7, 157, 112, 108, 175, 165, 240, 92, 103, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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