Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfe4ef3aaccb6f6b4322a9f9c98f1ac9abf65259ec18f22fe8997ab08ab57f59

Tx prefix hash: 5def24d23907454683f37ea68d8982e7c9e74f9974ef81bc9da37f01d296b0e0
Tx public key: 92a84f3081fb603fb3d0ff04006baec9c5cbb2677363366153c822cce377e55c
Timestamp: 1617142879 Timestamp [UCT]: 2021-03-30 22:21:19 Age [y:d:h:m:s]: 04:215:22:19:35
Block: 229987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172184 RingCT/type: yes/0
Extra: 0192a84f3081fb603fb3d0ff04006baec9c5cbb2677363366153c822cce377e55c02110000001f7071732b000000000000000000

1 output(s) for total of 106.163012336000 dcy

stealth address amount amount idx
00: 0c6120f01a9a0cdb713d88a3fa452ec123628ca21cae027bb0f855c83c26328f 106.163012336000 477281 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": 229997, "vin": [ { "gen": { "height": 229987 } } ], "vout": [ { "amount": 106163012336, "target": { "key": "0c6120f01a9a0cdb713d88a3fa452ec123628ca21cae027bb0f855c83c26328f" } } ], "extra": [ 1, 146, 168, 79, 48, 129, 251, 96, 63, 179, 208, 255, 4, 0, 107, 174, 201, 197, 203, 178, 103, 115, 99, 54, 97, 83, 200, 34, 204, 227, 119, 229, 92, 2, 17, 0, 0, 0, 31, 112, 113, 115, 43, 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