Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667efd7ca3c7369c83b2b78480f07e80bc2ee9bce67e7ff025480d73ffa9e4d4

Tx prefix hash: 3c6caf47b0f4731cc94a8cbe7e5458e00f0b17e7e286ae40e9b7631555fda507
Tx public key: 66317d0eda1cda80939b47340f81838e675f617586af5090038ac32de5d2ab7e
Timestamp: 1730639277 Timestamp [UCT]: 2024-11-03 13:07:57 Age [y:d:h:m:s]: 00:145:18:46:32
Block: 1145679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104011 RingCT/type: yes/0
Extra: 0166317d0eda1cda80939b47340f81838e675f617586af5090038ac32de5d2ab7e0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a63503e53f9a3cbe674faa6bae64b1dfd4259dcb2f5964ebd507a040578fb5af 0.600000000000 1630170 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": 1145689, "vin": [ { "gen": { "height": 1145679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a63503e53f9a3cbe674faa6bae64b1dfd4259dcb2f5964ebd507a040578fb5af" } } ], "extra": [ 1, 102, 49, 125, 14, 218, 28, 218, 128, 147, 155, 71, 52, 15, 129, 131, 142, 103, 95, 97, 117, 134, 175, 80, 144, 3, 138, 195, 45, 229, 210, 171, 126, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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