Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b4c53149acb0cc3b54b0fe67e47fc873bf68d2bdc3cf2057570924816cfda7

Tx prefix hash: 19870b0df8c7deaa60642c51da77d7910a5fed2aa3646011c8ef547bd7a4cc86
Tx public key: 1f9db1a220edaa779f7d0fcabd20bc86cf7c1d38c8c96725f94373e5ec8acf29
Timestamp: 1734747748 Timestamp [UCT]: 2024-12-21 02:22:28 Age [y:d:h:m:s]: 00:100:21:30:53
Block: 1179730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71876 RingCT/type: yes/0
Extra: 011f9db1a220edaa779f7d0fcabd20bc86cf7c1d38c8c96725f94373e5ec8acf290211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 262ce158f9b5b73c3d82d1ac9a558959def9689fc12f118f3c736bc1401c395d 0.600000000000 1666129 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": 1179740, "vin": [ { "gen": { "height": 1179730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "262ce158f9b5b73c3d82d1ac9a558959def9689fc12f118f3c736bc1401c395d" } } ], "extra": [ 1, 31, 157, 177, 162, 32, 237, 170, 119, 159, 125, 15, 202, 189, 32, 188, 134, 207, 124, 29, 56, 200, 201, 103, 37, 249, 67, 115, 229, 236, 138, 207, 41, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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