Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75001bc7797860f93e28f6d5d375d4a94ada1d686fe653f43f67c98ba289dabe

Tx prefix hash: 00b170bb0c2ad58f897f510d34a0d25d86f0d7bb1ef83bfcde362100ab862ef3
Tx public key: b47e42f85afe66aaf70e4bb22bd193a507df75a7ef224573a3769b5e102cd05e
Timestamp: 1740404587 Timestamp [UCT]: 2025-02-24 13:43:07 Age [y:d:h:m:s]: 00:071:17:07:50
Block: 1226251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51310 RingCT/type: yes/0
Extra: 01b47e42f85afe66aaf70e4bb22bd193a507df75a7ef224573a3769b5e102cd05e02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b18cf0fd2ff6787461d9d62cfd1f40318ffdf627fa9cbcf3ba5f5a568a3e3e17 0.600000000000 1713122 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": 1226261, "vin": [ { "gen": { "height": 1226251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b18cf0fd2ff6787461d9d62cfd1f40318ffdf627fa9cbcf3ba5f5a568a3e3e17" } } ], "extra": [ 1, 180, 126, 66, 248, 90, 254, 102, 170, 247, 14, 75, 178, 43, 209, 147, 165, 7, 223, 117, 167, 239, 34, 69, 115, 163, 118, 155, 94, 16, 44, 208, 94, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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