Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd2da4c7174862206d8421b46439be33aa955c3f34615886a2c41c08cb6b1d1e

Tx prefix hash: e3dbcef4ded3d3d68f7a75cc5e2150f33f1ef3f2d151506346c88d9f585eb8bf
Tx public key: f04f61e6554e74af7b12c2c51004f340d5569ee071d0df6b0b0c8197277d9b55
Timestamp: 1683496017 Timestamp [UCT]: 2023-05-07 21:46:57 Age [y:d:h:m:s]: 02:040:06:17:59
Block: 755180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550813 RingCT/type: yes/0
Extra: 01f04f61e6554e74af7b12c2c51004f340d5569ee071d0df6b0b0c8197277d9b55021100000003faf35c9c000000000000000000

1 output(s) for total of 1.930969284000 dcy

stealth address amount amount idx
00: 8fc98ae7dabea5de6980aacb63cc8e1786364c0b47a429a899b00d95884265c1 1.930969284000 1203485 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": 755190, "vin": [ { "gen": { "height": 755180 } } ], "vout": [ { "amount": 1930969284, "target": { "key": "8fc98ae7dabea5de6980aacb63cc8e1786364c0b47a429a899b00d95884265c1" } } ], "extra": [ 1, 240, 79, 97, 230, 85, 78, 116, 175, 123, 18, 194, 197, 16, 4, 243, 64, 213, 86, 158, 224, 113, 208, 223, 107, 11, 12, 129, 151, 39, 125, 155, 85, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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