Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be5fd24ab3ac7691c91b3637ad9ee3f4d3a4418f01c5a7f834fd923f80e6ec32

Tx prefix hash: 94d10f07ec6ebab009cf473ee39e1cdd828dc9975a6e4a8b03eb823f52dc825e
Tx public key: f17d0d9f5d0025557ef56c48ee9454ff1e39a8f3c20b08e8a37e922918aa781b
Timestamp: 1638395302 Timestamp [UCT]: 2021-12-01 21:48:22 Age [y:d:h:m:s]: 03:150:05:24:51
Block: 386367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 886087 RingCT/type: yes/0
Extra: 01f17d0d9f5d0025557ef56c48ee9454ff1e39a8f3c20b08e8a37e922918aa781b02110000000106faf294000000000000000000

1 output(s) for total of 32.196310853000 dcy

stealth address amount amount idx
00: 644c79e5749697a798d5107e0e39d38b13269a25d814cea8cef2e02f0aaf3245 32.196310853000 779504 of 0

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": 386377, "vin": [ { "gen": { "height": 386367 } } ], "vout": [ { "amount": 32196310853, "target": { "key": "644c79e5749697a798d5107e0e39d38b13269a25d814cea8cef2e02f0aaf3245" } } ], "extra": [ 1, 241, 125, 13, 159, 93, 0, 37, 85, 126, 245, 108, 72, 238, 148, 84, 255, 30, 57, 168, 243, 194, 11, 8, 232, 163, 126, 146, 41, 24, 170, 120, 27, 2, 17, 0, 0, 0, 1, 6, 250, 242, 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