Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14ae4c8fd86b68fe8ead280bf23788553b0c2d1344b5aab907f63db01353208

Tx prefix hash: 5c0455fbc819c02428bd076523bc31f9e350cfba57418a99b777c593ba17dfb4
Tx public key: bdc96b7b1c8baea7536cb25f75cfb06577facc70f6a9ef813303ae906187809c
Timestamp: 1723952094 Timestamp [UCT]: 2024-08-18 03:34:54 Age [y:d:h:m:s]: 00:228:10:38:59
Block: 1090321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163135 RingCT/type: yes/0
Extra: 01bdc96b7b1c8baea7536cb25f75cfb06577facc70f6a9ef813303ae906187809c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07f1db47e47ef0ed0c9123974bce26ff2827a3c1fc8a98b1daa50fc3ca2b15f5 0.600000000000 1564944 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": 1090331, "vin": [ { "gen": { "height": 1090321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07f1db47e47ef0ed0c9123974bce26ff2827a3c1fc8a98b1daa50fc3ca2b15f5" } } ], "extra": [ 1, 189, 201, 107, 123, 28, 139, 174, 167, 83, 108, 178, 95, 117, 207, 176, 101, 119, 250, 204, 112, 246, 169, 239, 129, 51, 3, 174, 144, 97, 135, 128, 156, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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