Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0ea0a3a79906ba1731310eba807c8f7c574d9a4e31bdac591611ca2347c7614

Tx prefix hash: cd055d6639cba5e2a994f17cf6f3502e7926fa8b73359d2c8470b201a9cda914
Tx public key: 17bbf00cc067a8947b0ecd34982f1c06d1a0e5fdce3d1fe434c266003e963c20
Timestamp: 1697421067 Timestamp [UCT]: 2023-10-16 01:51:07 Age [y:d:h:m:s]: 01:191:00:54:57
Block: 870566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397570 RingCT/type: yes/0
Extra: 0117bbf00cc067a8947b0ecd34982f1c06d1a0e5fdce3d1fe434c266003e963c2002110000000875e3f0e9000000000000000000

1 output(s) for total of 0.800669858000 dcy

stealth address amount amount idx
00: e276f67644c9978da86d426c7b6026b8c86a9975411c60f3e65af218e98e83c7 0.800669858000 1325449 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": 870576, "vin": [ { "gen": { "height": 870566 } } ], "vout": [ { "amount": 800669858, "target": { "key": "e276f67644c9978da86d426c7b6026b8c86a9975411c60f3e65af218e98e83c7" } } ], "extra": [ 1, 23, 187, 240, 12, 192, 103, 168, 148, 123, 14, 205, 52, 152, 47, 28, 6, 209, 160, 229, 253, 206, 61, 31, 228, 52, 194, 102, 0, 62, 150, 60, 32, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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