Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c36849161504fab465c289ce234155ff6725c9e36248bc79214e1ff19ada74

Tx prefix hash: 540796c8f48c4fc5ffec138f4645c227e1ab77d0a1ca4d1821c14ce1fa0afbda
Tx public key: 1346b1bc7b2caae58d7404253fb62541e2d241e0dea776f07b3cef8efcb0690d
Timestamp: 1583539716 Timestamp [UCT]: 2020-03-07 00:08:36 Age [y:d:h:m:s]: 04:308:10:06:11
Block: 77941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114873 RingCT/type: yes/0
Extra: 011346b1bc7b2caae58d7404253fb62541e2d241e0dea776f07b3cef8efcb0690d02110000002d8a2ee0d9000000000000000000

1 output(s) for total of 338.759653906000 dcy

stealth address amount amount idx
00: b63f9f7095675997d015ac529c40b60eae9c5c7b1ee6ed59105f4d799358004e 338.759653906000 143196 of 0

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": 77951, "vin": [ { "gen": { "height": 77941 } } ], "vout": [ { "amount": 338759653906, "target": { "key": "b63f9f7095675997d015ac529c40b60eae9c5c7b1ee6ed59105f4d799358004e" } } ], "extra": [ 1, 19, 70, 177, 188, 123, 44, 170, 229, 141, 116, 4, 37, 63, 182, 37, 65, 226, 210, 65, 224, 222, 167, 118, 240, 123, 60, 239, 142, 252, 176, 105, 13, 2, 17, 0, 0, 0, 45, 138, 46, 224, 217, 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