Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cefa7253dffa1d3fb1c02261f5f51656f45f4eb8c1e65cf8d3e13a33e63e2ca

Tx prefix hash: 0fcb3b6419e4413888a049df3e876dd9e8363c437890b376a4563841a8547ed1
Tx public key: c3e2f2a9b393721f85eb399ee8d6d866b7bf99307d57ea1c83007e9f198ceb67
Timestamp: 1730792052 Timestamp [UCT]: 2024-11-05 07:34:12 Age [y:d:h:m:s]: 00:145:23:09:27
Block: 1146948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104136 RingCT/type: yes/0
Extra: 01c3e2f2a9b393721f85eb399ee8d6d866b7bf99307d57ea1c83007e9f198ceb67021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89506c4d9a21f343ccd354c0075f25c83f3ac7d1f12ccad5254220b2243177e2 0.600000000000 1631641 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": 1146958, "vin": [ { "gen": { "height": 1146948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89506c4d9a21f343ccd354c0075f25c83f3ac7d1f12ccad5254220b2243177e2" } } ], "extra": [ 1, 195, 226, 242, 169, 179, 147, 114, 31, 133, 235, 57, 158, 232, 214, 216, 102, 183, 191, 153, 48, 125, 87, 234, 28, 131, 0, 126, 159, 25, 140, 235, 103, 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