Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb4bfe4af7af757dfc0f36cc193e874c3827399c7fb2df5575d94468b353b5f4

Tx prefix hash: ee9d4f3402cb1206ea6e42633cdc9fb94eaf9e4a33ae4c8bf6abe1bd962d7e11
Tx public key: cc5526c88566228d16cf24e6d884609b8e8b4cc896d73314ac797ff99dc463d9
Timestamp: 1575882962 Timestamp [UCT]: 2019-12-09 09:16:02 Age [y:d:h:m:s]: 04:353:09:16:55
Block: 23974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137604 RingCT/type: yes/0
Extra: 01cc5526c88566228d16cf24e6d884609b8e8b4cc896d73314ac797ff99dc463d9021100000014ad433a0b000000000000000000

1 output(s) for total of 511.169646185000 dcy

stealth address amount amount idx
00: 3c132a30e54532dc5870364aafbc59fbe29354f443c13d4f00d804220e417fca 511.169646185000 38875 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": 23984, "vin": [ { "gen": { "height": 23974 } } ], "vout": [ { "amount": 511169646185, "target": { "key": "3c132a30e54532dc5870364aafbc59fbe29354f443c13d4f00d804220e417fca" } } ], "extra": [ 1, 204, 85, 38, 200, 133, 102, 34, 141, 22, 207, 36, 230, 216, 132, 96, 155, 142, 139, 76, 200, 150, 215, 51, 20, 172, 121, 127, 249, 157, 196, 99, 217, 2, 17, 0, 0, 0, 20, 173, 67, 58, 11, 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