Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4207ff946396e3fd2e5c92d5611520e4600a48072c223c0ec7d3c1dafb3951

Tx prefix hash: aad2be29948bb9bcf4f739ca336f94f1b72303a8f3c694b5ce7cf22d15b2f0b5
Tx public key: ce774e3212f507769aade92f49f4a8962af6a70d28ffb96a145733188ed2bc19
Timestamp: 1636516907 Timestamp [UCT]: 2021-11-10 04:01:47 Age [y:d:h:m:s]: 03:048:10:51:18
Block: 371143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 813226 RingCT/type: yes/0
Extra: 01ce774e3212f507769aade92f49f4a8962af6a70d28ffb96a145733188ed2bc1902110000000242b3953e000000000000000000

1 output(s) for total of 36.161760442000 dcy

stealth address amount amount idx
00: 1fba1509773e498541b70414a16a9b503e6d55b1b2e0ee0703ce1cf99aa47009 36.161760442000 752171 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": 371153, "vin": [ { "gen": { "height": 371143 } } ], "vout": [ { "amount": 36161760442, "target": { "key": "1fba1509773e498541b70414a16a9b503e6d55b1b2e0ee0703ce1cf99aa47009" } } ], "extra": [ 1, 206, 119, 78, 50, 18, 245, 7, 118, 154, 173, 233, 47, 73, 244, 168, 150, 42, 246, 167, 13, 40, 255, 185, 106, 20, 87, 51, 24, 142, 210, 188, 25, 2, 17, 0, 0, 0, 2, 66, 179, 149, 62, 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