Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44b35950dfb862d13938ac794ac5ffba8f8100b6989ccb7406c71d7ac23e879

Tx prefix hash: 97743fd41ab56f352a944c38dcecccaaca64771128dcada474584bf0be00c198
Tx public key: 52df3e6c5f3ec940e4cf9bc95dc466bbd45a3be89641a5ebf0572e4cbef95a13
Timestamp: 1695972150 Timestamp [UCT]: 2023-09-29 07:22:30 Age [y:d:h:m:s]: 01:182:05:08:51
Block: 858560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391275 RingCT/type: yes/0
Extra: 0152df3e6c5f3ec940e4cf9bc95dc466bbd45a3be89641a5ebf0572e4cbef95a13021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.877474206000 dcy

stealth address amount amount idx
00: 31ff703cdb9a48da96ca2977faee97940dca1a14997c14204262fc6fcb3dda69 0.877474206000 1312742 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": 858570, "vin": [ { "gen": { "height": 858560 } } ], "vout": [ { "amount": 877474206, "target": { "key": "31ff703cdb9a48da96ca2977faee97940dca1a14997c14204262fc6fcb3dda69" } } ], "extra": [ 1, 82, 223, 62, 108, 95, 62, 201, 64, 228, 207, 155, 201, 93, 196, 102, 187, 212, 90, 59, 232, 150, 65, 165, 235, 240, 87, 46, 76, 190, 249, 90, 19, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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