Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f45cc0b3a37ec90c4a233de0869fbe8793e4036c1cd67233f8b58bfe11cdcea8

Tx prefix hash: ce29b318e8f8684451af4d7873d3de33e99cbe68b4e65d587adce700f6ce5953
Tx public key: a2a242a9f07326476044ee402a7e7f640680f62da0713aa0b1a088d24b4ce2e1
Timestamp: 1737190756 Timestamp [UCT]: 2025-01-18 08:59:16 Age [y:d:h:m:s]: 00:152:20:49:03
Block: 1199929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108941 RingCT/type: yes/0
Extra: 01a2a242a9f07326476044ee402a7e7f640680f62da0713aa0b1a088d24b4ce2e1021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808f38e8fedd906bc654ca6448a8b2f77b7641da04e05c55cea1f58c35698e62 0.600000000000 1686568 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": 1199939, "vin": [ { "gen": { "height": 1199929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808f38e8fedd906bc654ca6448a8b2f77b7641da04e05c55cea1f58c35698e62" } } ], "extra": [ 1, 162, 162, 66, 169, 240, 115, 38, 71, 96, 68, 238, 64, 42, 126, 127, 100, 6, 128, 246, 45, 160, 113, 58, 160, 177, 160, 136, 210, 75, 76, 226, 225, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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