Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2109750d4400f1c0806d95bbe7de41e08520b63acbf99c63d31babdf51488a7b

Tx prefix hash: 74e302211ceb6e40ddcd3c9acc6c7421744e26f02c183b5f74b1f37480453516
Tx public key: a8eb695b77f66834fdd2d4d7d77af89238aa09a96e6789e0a846709a50ec42ee
Timestamp: 1734774554 Timestamp [UCT]: 2024-12-21 09:49:14 Age [y:d:h:m:s]: 00:014:20:35:09
Block: 1179956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10608 RingCT/type: yes/0
Extra: 01a8eb695b77f66834fdd2d4d7d77af89238aa09a96e6789e0a846709a50ec42ee021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e933fb84d5cecd5c0e6e7b8dcbae2f3417ef60c3e02f9156e9adff5cf173864 0.600000000000 1666359 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": 1179966, "vin": [ { "gen": { "height": 1179956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e933fb84d5cecd5c0e6e7b8dcbae2f3417ef60c3e02f9156e9adff5cf173864" } } ], "extra": [ 1, 168, 235, 105, 91, 119, 246, 104, 52, 253, 210, 212, 215, 215, 122, 248, 146, 56, 170, 9, 169, 110, 103, 137, 224, 168, 70, 112, 154, 80, 236, 66, 238, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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