Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc940aa74f46cca5e4f1bd4846047be63fd2564671c6e844bca4b662725626ef

Tx prefix hash: 821dc664b6e455b72e46b81ba8e4d1f8d1440c9cbba65c302d9eca1bb1d49993
Tx public key: 914e099110337c91c88b42d1ca2182f2e0980b0e43dab952e5697aa249792da2
Timestamp: 1717378859 Timestamp [UCT]: 2024-06-03 01:40:59 Age [y:d:h:m:s]: 00:347:12:56:51
Block: 1035833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248399 RingCT/type: yes/0
Extra: 01914e099110337c91c88b42d1ca2182f2e0980b0e43dab952e5697aa249792da2021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f5a70e6c968016048b41597c361c348a9cd99522e168645ea01beaea9a809c9 0.600000000000 1504356 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": 1035843, "vin": [ { "gen": { "height": 1035833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f5a70e6c968016048b41597c361c348a9cd99522e168645ea01beaea9a809c9" } } ], "extra": [ 1, 145, 78, 9, 145, 16, 51, 124, 145, 200, 139, 66, 209, 202, 33, 130, 242, 224, 152, 11, 14, 67, 218, 185, 82, 229, 105, 122, 162, 73, 121, 45, 162, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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