Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0652cf094a06016307ad89943d022d624d358ef5e3e0e42613876638e70b9c3

Tx prefix hash: 43c668ed41ceb84aa946e999401dc63c5fbe6bde63c5a094a98aa68097ea7fc1
Tx public key: 6d932d0886c9dfc2daa607a09e6f9bf8b4fc2568e28bbcedd01ec1610357fe03
Timestamp: 1710619765 Timestamp [UCT]: 2024-03-16 20:09:25 Age [y:d:h:m:s]: 00:319:09:36:35
Block: 979809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228348 RingCT/type: yes/0
Extra: 016d932d0886c9dfc2daa607a09e6f9bf8b4fc2568e28bbcedd01ec1610357fe03021100000008679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0f5a19cefd6e9b3be6d8402c5d823bdafcb58887ef813df8a17200335b3843 0.600000000000 1439864 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": 979819, "vin": [ { "gen": { "height": 979809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0f5a19cefd6e9b3be6d8402c5d823bdafcb58887ef813df8a17200335b3843" } } ], "extra": [ 1, 109, 147, 45, 8, 134, 201, 223, 194, 218, 166, 7, 160, 158, 111, 155, 248, 180, 252, 37, 104, 226, 139, 188, 237, 208, 30, 193, 97, 3, 87, 254, 3, 2, 17, 0, 0, 0, 8, 103, 154, 138, 129, 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