Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b23f21264396e86b972f9b08a149aab89e3577fbe02e56c572fe456c982da2

Tx prefix hash: 264e43655dff2fc668c4ad359d0f2baf7e803f6f85446a12135de5831a00ae05
Tx public key: a05458a93e4bb96bf5b10d7acc7772f03ef1f04d55e0cfcf2627f1706c5feb4c
Timestamp: 1706733215 Timestamp [UCT]: 2024-01-31 20:33:35 Age [y:d:h:m:s]: 01:058:16:46:00
Block: 947549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303017 RingCT/type: yes/0
Extra: 01a05458a93e4bb96bf5b10d7acc7772f03ef1f04d55e0cfcf2627f1706c5feb4c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07ba9c0f208af1e633065f8c45eaed5cc33decfb610b04a65f95d47474ad7544 0.600000000000 1405901 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": 947559, "vin": [ { "gen": { "height": 947549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07ba9c0f208af1e633065f8c45eaed5cc33decfb610b04a65f95d47474ad7544" } } ], "extra": [ 1, 160, 84, 88, 169, 62, 75, 185, 107, 245, 177, 13, 122, 204, 119, 114, 240, 62, 241, 240, 77, 85, 224, 207, 207, 38, 39, 241, 112, 108, 95, 235, 76, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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