Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8310f038fbab5c32d7e689cfcee95b2ba51668a22b31f6c277503842bb05a3ce

Tx prefix hash: cd137606a7b0fc07162f9752be9f1a8e961d2181af5e2e692d596b724293101a
Tx public key: 6bfdc49cb6ab3756d57f9764ef1b9b67da2c8862f7c8a4566040b6856d99853e
Timestamp: 1735706047 Timestamp [UCT]: 2025-01-01 04:34:07 Age [y:d:h:m:s]: 00:165:06:43:09
Block: 1187629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117870 RingCT/type: yes/0
Extra: 016bfdc49cb6ab3756d57f9764ef1b9b67da2c8862f7c8a4566040b6856d99853e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2b68db8ab69f050327be8a84429320697857f1dfe696b7e5c00d6c0b1986bd2 0.600000000000 1674122 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": 1187639, "vin": [ { "gen": { "height": 1187629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2b68db8ab69f050327be8a84429320697857f1dfe696b7e5c00d6c0b1986bd2" } } ], "extra": [ 1, 107, 253, 196, 156, 182, 171, 55, 86, 213, 127, 151, 100, 239, 27, 155, 103, 218, 44, 136, 98, 247, 200, 164, 86, 96, 64, 182, 133, 109, 153, 133, 62, 2, 17, 0, 0, 0, 4, 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