Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92f81c6df6674f27be158b74bfa1c7991d3de26e5d86198446aa298d3d094165

Tx prefix hash: 2d331da485a3b55f25178386dcd18a8d85ae8a40da3905883dda3d3b908c2303
Tx public key: c36528f6099c95bd4e3ef324aad71a3a724f89c7d7c5421b15b641c70f23da64
Timestamp: 1736912339 Timestamp [UCT]: 2025-01-15 03:38:59 Age [y:d:h:m:s]: 00:155:14:15:08
Block: 1197617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110901 RingCT/type: yes/0
Extra: 01c36528f6099c95bd4e3ef324aad71a3a724f89c7d7c5421b15b641c70f23da64021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d795ae0f3fe13e5a4a94d047f716c0599017a1a48cc5b39c89fc4703493ef2d 0.600000000000 1684230 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": 1197627, "vin": [ { "gen": { "height": 1197617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d795ae0f3fe13e5a4a94d047f716c0599017a1a48cc5b39c89fc4703493ef2d" } } ], "extra": [ 1, 195, 101, 40, 246, 9, 156, 149, 189, 78, 62, 243, 36, 170, 215, 26, 58, 114, 79, 137, 199, 215, 197, 66, 27, 21, 182, 65, 199, 15, 35, 218, 100, 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