Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68e1f7755892f56a35b7d234d1a0ae21d46d9cb6de0b78ec2d74753b6239c68

Tx prefix hash: a8f69f2c63d11ade9e8e69f2cb2d47e8c73810eae694ce794139c23e3210d859
Tx public key: 3543b90379b7b1ef23b7d47c0637f178bec12efcd466e1085535f93e3c5fa003
Timestamp: 1701545226 Timestamp [UCT]: 2023-12-02 19:27:06 Age [y:d:h:m:s]: 01:311:08:58:24
Block: 904553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481376 RingCT/type: yes/0
Extra: 013543b90379b7b1ef23b7d47c0637f178bec12efcd466e1085535f93e3c5fa00302110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.617789311000 dcy

stealth address amount amount idx
00: 0083351b6f2086433a13c8c186665d1a8c8aab6fbe2465182ea3904008085639 0.617789311000 1361314 of 0

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": 904563, "vin": [ { "gen": { "height": 904553 } } ], "vout": [ { "amount": 617789311, "target": { "key": "0083351b6f2086433a13c8c186665d1a8c8aab6fbe2465182ea3904008085639" } } ], "extra": [ 1, 53, 67, 185, 3, 121, 183, 177, 239, 35, 183, 212, 124, 6, 55, 241, 120, 190, 193, 46, 252, 212, 102, 225, 8, 85, 53, 249, 62, 60, 95, 160, 3, 2, 17, 0, 0, 0, 13, 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