Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356ee48a5deab6a83ce147c8b986bc9e4859654c5719c34bc9b22735aa1bc679

Tx prefix hash: c4f36aaf2f256f2e5b381b7ab3f593a69db493a319faca2047c1bf26095519e8
Tx public key: 2b3c1043739a3f952ba2fbd03b106efdc506fd82b0542701af2aa871441bbe3d
Timestamp: 1722724454 Timestamp [UCT]: 2024-08-03 22:34:14 Age [y:d:h:m:s]: 00:257:11:53:08
Block: 1080139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183943 RingCT/type: yes/0
Extra: 012b3c1043739a3f952ba2fbd03b106efdc506fd82b0542701af2aa871441bbe3d02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0246cd32f78cacbc16b57d331529c0d3d1d905de45522baf538efc5f33336e2 0.600000000000 1553388 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": 1080149, "vin": [ { "gen": { "height": 1080139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0246cd32f78cacbc16b57d331529c0d3d1d905de45522baf538efc5f33336e2" } } ], "extra": [ 1, 43, 60, 16, 67, 115, 154, 63, 149, 43, 162, 251, 208, 59, 16, 110, 253, 197, 6, 253, 130, 176, 84, 39, 1, 175, 42, 168, 113, 68, 27, 190, 61, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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