Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428ddee367f4ce80b2165bf4f9d76e191b2105dcd9038e193027c790772eeb9d

Tx prefix hash: 2e2484b93c011df47f131f98c062840606efa48c0f9b9a5f149ba81bfd450708
Tx public key: 7fa4b0d0fd98ddcb843ec2396e53add374916bfb801e427b8d24ae61ee9faa5c
Timestamp: 1674637641 Timestamp [UCT]: 2023-01-25 09:07:21 Age [y:d:h:m:s]: 01:353:16:16:51
Block: 682360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513761 RingCT/type: yes/0
Extra: 017fa4b0d0fd98ddcb843ec2396e53add374916bfb801e427b8d24ae61ee9faa5c02110000000674b6d784000000000000000000

1 output(s) for total of 3.365565119000 dcy

stealth address amount amount idx
00: 63bc92c9f135469d972920785126d6004d1305cdb85c50bac13c0e91d17bfc15 3.365565119000 1124479 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": 682370, "vin": [ { "gen": { "height": 682360 } } ], "vout": [ { "amount": 3365565119, "target": { "key": "63bc92c9f135469d972920785126d6004d1305cdb85c50bac13c0e91d17bfc15" } } ], "extra": [ 1, 127, 164, 176, 208, 253, 152, 221, 203, 132, 62, 194, 57, 110, 83, 173, 211, 116, 145, 107, 251, 128, 30, 66, 123, 141, 36, 174, 97, 238, 159, 170, 92, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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