Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f3d5554212ca22192261910c6a65c76880d0fbcab7dd5ebcafa23916d3703af

Tx prefix hash: 9359709b1dfd37924e2fab2a90f7b1d046e10cebd383c61cf8d3667adf066d7e
Tx public key: 1bd094d13ccd7ac9f9f60a2d913012871fea3a5033f2c5a87ae9d243e1a7a2fe
Timestamp: 1723742780 Timestamp [UCT]: 2024-08-15 17:26:20 Age [y:d:h:m:s]: 00:287:00:36:22
Block: 1088579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205061 RingCT/type: yes/0
Extra: 011bd094d13ccd7ac9f9f60a2d913012871fea3a5033f2c5a87ae9d243e1a7a2fe021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47e8b2e9a13b8649aafe99bc722112db770f40c2c80de5396569cf89eaa1b43e 0.600000000000 1563196 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": 1088589, "vin": [ { "gen": { "height": 1088579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47e8b2e9a13b8649aafe99bc722112db770f40c2c80de5396569cf89eaa1b43e" } } ], "extra": [ 1, 27, 208, 148, 209, 60, 205, 122, 201, 249, 246, 10, 45, 145, 48, 18, 135, 31, 234, 58, 80, 51, 242, 197, 168, 122, 233, 210, 67, 225, 167, 162, 254, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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