Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b05c0568c2044460fda4d57a45258aeae9f787ec0bace6c8ae9b8872d295be1

Tx prefix hash: 5422cfc0e80a8684680d9fb6bad3650ba3eec3016a3d8cc0ccbae339ebcf36c9
Tx public key: d5f03421b0b60e956abb5ceb7cdabd1db6206d2a006f49cd7a20ebde6b6c7cf6
Timestamp: 1695944707 Timestamp [UCT]: 2023-09-28 23:45:07 Age [y:d:h:m:s]: 01:243:00:42:39
Block: 858332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434787 RingCT/type: yes/0
Extra: 01d5f03421b0b60e956abb5ceb7cdabd1db6206d2a006f49cd7a20ebde6b6c7cf6021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.879001908000 dcy

stealth address amount amount idx
00: 83be429aa7e2745f6666411a75f835c77557f4baa6d373f46b20efbd2f2b227e 0.879001908000 1312502 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": 858342, "vin": [ { "gen": { "height": 858332 } } ], "vout": [ { "amount": 879001908, "target": { "key": "83be429aa7e2745f6666411a75f835c77557f4baa6d373f46b20efbd2f2b227e" } } ], "extra": [ 1, 213, 240, 52, 33, 176, 182, 14, 149, 106, 187, 92, 235, 124, 218, 189, 29, 182, 32, 109, 42, 0, 111, 73, 205, 122, 32, 235, 222, 107, 108, 124, 246, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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