Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49745565bf2cf93c161b0c59614e105e056b29b6254e544822001a0f55a1371c

Tx prefix hash: bf7c0723286acb63e1c9a7c77dd4c82c3c9ee1c79ef574b386bae8d71b071c46
Tx public key: e8532577186ebcaa08fcebff16195d6dfc065b6316f07e98dfb3afdd75dcb7c3
Timestamp: 1735801532 Timestamp [UCT]: 2025-01-02 07:05:32 Age [y:d:h:m:s]: 00:321:19:09:52
Block: 1188426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227511 RingCT/type: yes/0
Extra: 01e8532577186ebcaa08fcebff16195d6dfc065b6316f07e98dfb3afdd75dcb7c3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac1620c7bf4ed34582341b92a2e9fb3408086058fe4cc3db9d3a44da3f5cecad 0.600000000000 1674927 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": 1188436, "vin": [ { "gen": { "height": 1188426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac1620c7bf4ed34582341b92a2e9fb3408086058fe4cc3db9d3a44da3f5cecad" } } ], "extra": [ 1, 232, 83, 37, 119, 24, 110, 188, 170, 8, 252, 235, 255, 22, 25, 93, 109, 252, 6, 91, 99, 22, 240, 126, 152, 223, 179, 175, 221, 117, 220, 183, 195, 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