Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9749cdbb133cf42c5341fe0202900eb96b441520d94de0b439b6eb2a796b3a

Tx prefix hash: 63346f46823bb1ed6dc81f82737512d568c30d94ad98ab34a2ef1b93ed668c3a
Tx public key: c6dbd2982b798fa82f941c725661e4aa846c3eac81b0c83b8bde38fce1a28bb8
Timestamp: 1703931308 Timestamp [UCT]: 2023-12-30 10:15:08 Age [y:d:h:m:s]: 01:027:10:42:02
Block: 924338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280912 RingCT/type: yes/0
Extra: 01c6dbd2982b798fa82f941c725661e4aa846c3eac81b0c83b8bde38fce1a28bb8021100000011ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce5f97bf679dd46f714723b3743b3a3ae5be4f0fcf9fb6788ed89d48f89373af 0.600000000000 1382084 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": 924348, "vin": [ { "gen": { "height": 924338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce5f97bf679dd46f714723b3743b3a3ae5be4f0fcf9fb6788ed89d48f89373af" } } ], "extra": [ 1, 198, 219, 210, 152, 43, 121, 143, 168, 47, 148, 28, 114, 86, 97, 228, 170, 132, 108, 62, 172, 129, 176, 200, 59, 139, 222, 56, 252, 225, 162, 139, 184, 2, 17, 0, 0, 0, 17, 172, 50, 141, 17, 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