Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf274827bc7059a2a2c2c967b41b973a40b42f281e20dc96d86d6e8ebec4d58f

Tx prefix hash: 9eae811259e5cb0150184557787d31cd8168298c4c63aac12685ee08c9139b2b
Tx public key: cd9eed0d782591830cebd8496c6ad23debe71c8fc8a3cf6b4b081ebdf2140190
Timestamp: 1706749156 Timestamp [UCT]: 2024-02-01 00:59:16 Age [y:d:h:m:s]: 01:054:11:15:20
Block: 947679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299988 RingCT/type: yes/0
Extra: 01cd9eed0d782591830cebd8496c6ad23debe71c8fc8a3cf6b4b081ebdf21401900211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e308ba4002146a00b41b50c0d765e375aef005a2d4a8721fe8a7386a3b5cbf 0.600000000000 1406037 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": 947689, "vin": [ { "gen": { "height": 947679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e308ba4002146a00b41b50c0d765e375aef005a2d4a8721fe8a7386a3b5cbf" } } ], "extra": [ 1, 205, 158, 237, 13, 120, 37, 145, 131, 12, 235, 216, 73, 108, 106, 210, 61, 235, 231, 28, 143, 200, 163, 207, 107, 75, 8, 30, 189, 242, 20, 1, 144, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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