Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87e76c8c744054573266d07075f35abf5330d22be0f85d3a0868709129e62921

Tx prefix hash: f8324252b0eab8bfc0aa4f0775c2eaeec32bb7b30cc99693865ff884d2fd4fb6
Tx public key: 2d30b3b7052842e2b18d14257b827da2e85bcd7b65e1c6757087ba1bad815102
Timestamp: 1742528672 Timestamp [UCT]: 2025-03-21 03:44:32 Age [y:d:h:m:s]: 00:201:01:29:15
Block: 1243872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141348 RingCT/type: yes/0
Extra: 012d30b3b7052842e2b18d14257b827da2e85bcd7b65e1c6757087ba1bad815102021100000001bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf8b968b67fdd583e60b4d1a84184760f4b79a0f522d5d184dc64b49ebb9f020 0.600000000000 1730863 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": 1243882, "vin": [ { "gen": { "height": 1243872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf8b968b67fdd583e60b4d1a84184760f4b79a0f522d5d184dc64b49ebb9f020" } } ], "extra": [ 1, 45, 48, 179, 183, 5, 40, 66, 226, 177, 141, 20, 37, 123, 130, 125, 162, 232, 91, 205, 123, 101, 225, 198, 117, 112, 135, 186, 27, 173, 129, 81, 2, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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