Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733a2674c5281b54254bcdc7cb6719c770ee7770bbb1756825e7adc4a35f5a8b

Tx prefix hash: d47ce7b1319e4146b490c9e9f2a1eaac4488de125a9e271d1a628256b1d91a34
Tx public key: a14581675d7651587cf438d68f14e07562387d37ed8559bfe0f9f51db13a7601
Timestamp: 1695576316 Timestamp [UCT]: 2023-09-24 17:25:16 Age [y:d:h:m:s]: 01:270:14:28:45
Block: 855265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454346 RingCT/type: yes/0
Extra: 01a14581675d7651587cf438d68f14e07562387d37ed8559bfe0f9f51db13a7601021100000005faf35c9c000000000000000000

1 output(s) for total of 0.899812592000 dcy

stealth address amount amount idx
00: 50f6fc2d1fbfa1b1d30e790cf4be5866d0386b9c9b180121c7cfa9ffb1cc9780 0.899812592000 1309279 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": 855275, "vin": [ { "gen": { "height": 855265 } } ], "vout": [ { "amount": 899812592, "target": { "key": "50f6fc2d1fbfa1b1d30e790cf4be5866d0386b9c9b180121c7cfa9ffb1cc9780" } } ], "extra": [ 1, 161, 69, 129, 103, 93, 118, 81, 88, 124, 244, 56, 214, 143, 20, 224, 117, 98, 56, 125, 55, 237, 133, 89, 191, 224, 249, 245, 29, 177, 58, 118, 1, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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