Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcedd4ccbf06bf38a8f562f004b5515921fde20b947fea22242ebcdce7e9e6e3

Tx prefix hash: 35dc9686aa7891d7b2ac60e754a908008dfbe5c852242e3eee1f82dc1e03c4a0
Tx public key: 2c6f616f614295343bf5a6b624872d36940dfdd33cda5f37bfeba835f8af45b1
Timestamp: 1725086245 Timestamp [UCT]: 2024-08-31 06:37:25 Age [y:d:h:m:s]: 00:089:03:41:39
Block: 1099724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63761 RingCT/type: yes/0
Extra: 012c6f616f614295343bf5a6b624872d36940dfdd33cda5f37bfeba835f8af45b102110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d2d15e4bac486d5e1f1dc0f6d17e4dba2cfff10fd6d44e20c2321a73e2dcd02 0.600000000000 1575691 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": 1099734, "vin": [ { "gen": { "height": 1099724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d2d15e4bac486d5e1f1dc0f6d17e4dba2cfff10fd6d44e20c2321a73e2dcd02" } } ], "extra": [ 1, 44, 111, 97, 111, 97, 66, 149, 52, 59, 245, 166, 182, 36, 135, 45, 54, 148, 13, 253, 211, 60, 218, 95, 55, 191, 235, 168, 53, 248, 175, 69, 177, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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