Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61e95b6b044693128c317dfb1e8e676889ee2db2af2818766a2445033f2c7b39

Tx prefix hash: 5d9ebec27d45c02555e3e790be5f8080d848c3c31ad0ae2eb64e4d7947961b68
Tx public key: 952ad82999962674dad491d7e4ee6046ff391c9ea2b4c67d878c64c09ceb9889
Timestamp: 1708321562 Timestamp [UCT]: 2024-02-19 05:46:02 Age [y:d:h:m:s]: 01:263:06:22:28
Block: 960736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446896 RingCT/type: yes/0
Extra: 01952ad82999962674dad491d7e4ee6046ff391c9ea2b4c67d878c64c09ceb98890211000000016179ba94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0a746f86f08aaeb2bdf6c86a6d0c56a5d9a5aefda49ee87b1211f93e77c3eea 0.600000000000 1420323 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": 960746, "vin": [ { "gen": { "height": 960736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0a746f86f08aaeb2bdf6c86a6d0c56a5d9a5aefda49ee87b1211f93e77c3eea" } } ], "extra": [ 1, 149, 42, 216, 41, 153, 150, 38, 116, 218, 212, 145, 215, 228, 238, 96, 70, 255, 57, 28, 158, 162, 180, 198, 125, 135, 140, 100, 192, 156, 235, 152, 137, 2, 17, 0, 0, 0, 1, 97, 121, 186, 148, 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