Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 474668e2ee0e8ba560a230f0b0dc4bbf3a1fd382f68fe4b6d937719c30c73b48

Tx prefix hash: 0e53693a6781aa8de9b45bdade698bd7431c71cae13cd49b028d544e02c9c68a
Tx public key: 4381d7138897268964447d57580a7f5914b7b6efdb9db692b59da680434dbeb5
Timestamp: 1736109138 Timestamp [UCT]: 2025-01-05 20:32:18 Age [y:d:h:m:s]: 00:091:05:08:05
Block: 1190981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64954 RingCT/type: yes/0
Extra: 014381d7138897268964447d57580a7f5914b7b6efdb9db692b59da680434dbeb50211000000171f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d9d868f8fef309d62a06278ed7e7d9f1241f43f6f841544eabf5bc0f7b7f7c4 0.600000000000 1677504 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": 1190991, "vin": [ { "gen": { "height": 1190981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d9d868f8fef309d62a06278ed7e7d9f1241f43f6f841544eabf5bc0f7b7f7c4" } } ], "extra": [ 1, 67, 129, 215, 19, 136, 151, 38, 137, 100, 68, 125, 87, 88, 10, 127, 89, 20, 183, 182, 239, 219, 157, 182, 146, 181, 157, 166, 128, 67, 77, 190, 181, 2, 17, 0, 0, 0, 23, 31, 10, 83, 235, 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