Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb4e66cd3aa0a2e62ad78cf7b5a93bdc31e4555550f39c538ac58659a2dba5db

Tx prefix hash: 0e90e22cfec0986d7311b1415879ea61d71eb468d00641b7734bae6ea64ab08a
Tx public key: 5a11fc6249eda07ba46ea9dbe9184cbc5114304f0bee8ba7c1535f58c52687a4
Timestamp: 1731259892 Timestamp [UCT]: 2024-11-10 17:31:32 Age [y:d:h:m:s]: 00:131:19:36:41
Block: 1150816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94035 RingCT/type: yes/0
Extra: 015a11fc6249eda07ba46ea9dbe9184cbc5114304f0bee8ba7c1535f58c52687a4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03b08ca65f3a9273172b76ae906ef9b7ac6407d5e10ea2459daa2f8e5f18e47c 0.600000000000 1636225 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": 1150826, "vin": [ { "gen": { "height": 1150816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03b08ca65f3a9273172b76ae906ef9b7ac6407d5e10ea2459daa2f8e5f18e47c" } } ], "extra": [ 1, 90, 17, 252, 98, 73, 237, 160, 123, 164, 110, 169, 219, 233, 24, 76, 188, 81, 20, 48, 79, 11, 238, 139, 167, 193, 83, 95, 88, 197, 38, 135, 164, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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