Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29709bf9272904019c56a6a9be29366fa849648fd2a3c6b59e63b215b27da34

Tx prefix hash: 56260f8c90f1f9153d8688e2d534fb3c09f68c150743861910a5f4c0da81847b
Tx public key: 18b7d0e950a8b21c8732d341d94ba95dcc48ce6221951714949c6976d0f04f94
Timestamp: 1732571018 Timestamp [UCT]: 2024-11-25 21:43:38 Age [y:d:h:m:s]: 00:152:14:50:58
Block: 1161673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108912 RingCT/type: yes/0
Extra: 0118b7d0e950a8b21c8732d341d94ba95dcc48ce6221951714949c6976d0f04f94021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5785e4fb9bdfcd9e88dafd59bada4f70ebc5fdaed201262a4cc5dc9e5a4a788c 0.600000000000 1647328 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": 1161683, "vin": [ { "gen": { "height": 1161673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5785e4fb9bdfcd9e88dafd59bada4f70ebc5fdaed201262a4cc5dc9e5a4a788c" } } ], "extra": [ 1, 24, 183, 208, 233, 80, 168, 178, 28, 135, 50, 211, 65, 217, 75, 169, 93, 204, 72, 206, 98, 33, 149, 23, 20, 148, 156, 105, 118, 208, 240, 79, 148, 2, 17, 0, 0, 0, 3, 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