Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ff51ab76b4f2472a048760ad2f047ff74763263b9831eb59a8d9843578ad231

Tx prefix hash: 23758441760b6eeea810875b921e60aca26112a63367969175a6d73af41537a3
Tx public key: e702676916d32debf55d1b4c48d545b463c7e7e2393c9cb3578ce3b7f7a1fce3
Timestamp: 1733720275 Timestamp [UCT]: 2024-12-09 04:57:55 Age [y:d:h:m:s]: 00:113:05:46:04
Block: 1171199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80719 RingCT/type: yes/0
Extra: 01e702676916d32debf55d1b4c48d545b463c7e7e2393c9cb3578ce3b7f7a1fce3021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37223a1fe8310f9302ebbcbf3eec1a87e6e3a3b766fdac1e48781d6d10175ef0 0.600000000000 1656938 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": 1171209, "vin": [ { "gen": { "height": 1171199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37223a1fe8310f9302ebbcbf3eec1a87e6e3a3b766fdac1e48781d6d10175ef0" } } ], "extra": [ 1, 231, 2, 103, 105, 22, 211, 45, 235, 245, 93, 27, 76, 72, 213, 69, 180, 99, 199, 231, 226, 57, 60, 156, 179, 87, 140, 227, 183, 247, 161, 252, 227, 2, 17, 0, 0, 0, 6, 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