Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21fb485066e7944eba9e75845f7ed229c1de9dd5a48a3f8408f3973e20739241

Tx prefix hash: bd00fee04ec3c67483192004556e46e5b0b8148cfbf7cf05220a506602f0973a
Tx public key: ee6b40795f5cbf849f735edfb2ea8647ed1a8578a69e6c906af92dbe42712e8b
Timestamp: 1717521798 Timestamp [UCT]: 2024-06-04 17:23:18 Age [y:d:h:m:s]: 00:341:10:05:49
Block: 1037018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244012 RingCT/type: yes/0
Extra: 01ee6b40795f5cbf849f735edfb2ea8647ed1a8578a69e6c906af92dbe42712e8b0211000000024385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b9a93de90a0e4a5219fa45ac63bd22db83a4a871c1c17ced4df7c47af59e130 0.600000000000 1505549 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": 1037028, "vin": [ { "gen": { "height": 1037018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b9a93de90a0e4a5219fa45ac63bd22db83a4a871c1c17ced4df7c47af59e130" } } ], "extra": [ 1, 238, 107, 64, 121, 95, 92, 191, 132, 159, 115, 94, 223, 178, 234, 134, 71, 237, 26, 133, 120, 166, 158, 108, 144, 106, 249, 45, 190, 66, 113, 46, 139, 2, 17, 0, 0, 0, 2, 67, 133, 54, 42, 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