Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a951973b295cc66ed37bad7fc9e2e4dda7457ae59e9f9edd8927b26492e70f32

Tx prefix hash: a7a1fc4326fc362a042f5305c42007ce9b31c51f25c71c7589c2c7ce1247fcff
Tx public key: 62ac073e5a0eb55be12f10fccf7978541bcdc622b42a03b48e3e8a5f769a33f0
Timestamp: 1717486632 Timestamp [UCT]: 2024-06-04 07:37:12 Age [y:d:h:m:s]: 00:288:14:40:32
Block: 1036735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206263 RingCT/type: yes/0
Extra: 0162ac073e5a0eb55be12f10fccf7978541bcdc622b42a03b48e3e8a5f769a33f00211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45032fdf494e3f4c93f5c455dc8e349d453659685ef4424adb755ce3e1e200a9 0.600000000000 1505264 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": 1036745, "vin": [ { "gen": { "height": 1036735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45032fdf494e3f4c93f5c455dc8e349d453659685ef4424adb755ce3e1e200a9" } } ], "extra": [ 1, 98, 172, 7, 62, 90, 14, 181, 91, 225, 47, 16, 252, 207, 121, 120, 84, 27, 205, 198, 34, 180, 42, 3, 180, 142, 62, 138, 95, 118, 154, 51, 240, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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