Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80a5fbdf0092fc32cf68353cb1aeee5cd348d5cae17483aff50d7a4322e31de6

Tx prefix hash: b6ac3ec1b9435119a249986e2526dded94b4ecb11fa51ccd3d5d62099daf68fb
Tx public key: e0a9178ae9a9312a95a10a815b7e01bdbf3c1e15124466f5cfdcebd337b90c6f
Timestamp: 1714369659 Timestamp [UCT]: 2024-04-29 05:47:39 Age [y:d:h:m:s]: 00:343:16:55:00
Block: 1010873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245686 RingCT/type: yes/0
Extra: 01e0a9178ae9a9312a95a10a815b7e01bdbf3c1e15124466f5cfdcebd337b90c6f0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: babcb36fd9b8ecc7e177eb370d6cba711e79386336f2ee7bc37e2f734b5188c6 0.600000000000 1472943 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": 1010883, "vin": [ { "gen": { "height": 1010873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "babcb36fd9b8ecc7e177eb370d6cba711e79386336f2ee7bc37e2f734b5188c6" } } ], "extra": [ 1, 224, 169, 23, 138, 233, 169, 49, 42, 149, 161, 10, 129, 91, 126, 1, 189, 191, 60, 30, 21, 18, 68, 102, 245, 207, 220, 235, 211, 55, 185, 12, 111, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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