Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7330a6988897f23d10fdfb02e6fd2f6a79c1fb82d9ebfc610bf06f6bf3868d12

Tx prefix hash: 6af15d835cc830152ed8be572b46439872198408e2d3a96003cbd0eacdcaf9d9
Tx public key: 5f897c3d8865da553fbe33ce338461b6afd88a2a595d3e2f52bc63ede9ca0f57
Timestamp: 1708463341 Timestamp [UCT]: 2024-02-20 21:09:01 Age [y:d:h:m:s]: 01:036:03:42:59
Block: 961906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286860 RingCT/type: yes/0
Extra: 015f897c3d8865da553fbe33ce338461b6afd88a2a595d3e2f52bc63ede9ca0f570211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 407dc96f1467c63e4171bc730eac5eae3d19b5f52a20baf46da57dfca69cd956 0.600000000000 1421521 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": 961916, "vin": [ { "gen": { "height": 961906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "407dc96f1467c63e4171bc730eac5eae3d19b5f52a20baf46da57dfca69cd956" } } ], "extra": [ 1, 95, 137, 124, 61, 136, 101, 218, 85, 63, 190, 51, 206, 51, 132, 97, 182, 175, 216, 138, 42, 89, 93, 62, 47, 82, 188, 99, 237, 233, 202, 15, 87, 2, 17, 0, 0, 0, 2, 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