Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fd5f312efeb9161d492ed157f311697fdc4c6c5c3a67669317f040a318821fe

Tx prefix hash: 6665110858bcc3ae5da33ed354bbb12536774b48ec2a8a571e6977ebb894ab16
Tx public key: 581333c94f7fc95da16280d7dfb3c4f23122a0e9e902f3af10b8a7f3179df4af
Timestamp: 1633329547 Timestamp [UCT]: 2021-10-04 06:39:07 Age [y:d:h:m:s]: 03:122:02:06:34
Block: 346332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864051 RingCT/type: yes/0
Extra: 01581333c94f7fc95da16280d7dfb3c4f23122a0e9e902f3af10b8a7f3179df4af021100000002f29d7abf000000000000000000

1 output(s) for total of 43.697716531000 dcy

stealth address amount amount idx
00: ae8e2a6874ff833ea7d0aecb93bfd89aa11f333ebeca357272a660a5a89c4fa1 43.697716531000 710168 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": 346342, "vin": [ { "gen": { "height": 346332 } } ], "vout": [ { "amount": 43697716531, "target": { "key": "ae8e2a6874ff833ea7d0aecb93bfd89aa11f333ebeca357272a660a5a89c4fa1" } } ], "extra": [ 1, 88, 19, 51, 201, 79, 127, 201, 93, 161, 98, 128, 215, 223, 179, 196, 242, 49, 34, 160, 233, 233, 2, 243, 175, 16, 184, 167, 243, 23, 157, 244, 175, 2, 17, 0, 0, 0, 2, 242, 157, 122, 191, 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