Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e9788fc7974fbf6b64aa8ba4d1d60c1d92cb728197bcb7bdd6385e2d2832832

Tx prefix hash: d272d5dbd4263a7a9b92a75b46644db1a567011651e0963e5389211e5e0f99c4
Tx public key: 18335243d2167b93519b7aa1bc96addebcda38ae2f17998ab0cd34810914c226
Timestamp: 1734603860 Timestamp [UCT]: 2024-12-19 10:24:20 Age [y:d:h:m:s]: 00:104:23:37:55
Block: 1178532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74799 RingCT/type: yes/0
Extra: 0118335243d2167b93519b7aa1bc96addebcda38ae2f17998ab0cd34810914c2260211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf0ce1e7e1fcc39bb72c9e41da3794c097dfd1b92da15874cbeee6ca68a22a00 0.600000000000 1664919 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": 1178542, "vin": [ { "gen": { "height": 1178532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf0ce1e7e1fcc39bb72c9e41da3794c097dfd1b92da15874cbeee6ca68a22a00" } } ], "extra": [ 1, 24, 51, 82, 67, 210, 22, 123, 147, 81, 155, 122, 161, 188, 150, 173, 222, 188, 218, 56, 174, 47, 23, 153, 138, 176, 205, 52, 129, 9, 20, 194, 38, 2, 17, 0, 0, 0, 4, 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