Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ddc58eb1b8ba88fb7b9986f83ba6135e58fda2091decce00271421c5b2c67c

Tx prefix hash: 52fbbcf54554b501cf50dda107703edee4cc06ce5da3e2d9e032b8bf77f0fe3d
Tx public key: 2fce389f0b5039338f1150e8b774326dc492aaa8ef458c482149156a6c5add25
Timestamp: 1687113368 Timestamp [UCT]: 2023-06-18 18:36:08 Age [y:d:h:m:s]: 01:212:18:15:13
Block: 785161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413440 RingCT/type: yes/0
Extra: 012fce389f0b5039338f1150e8b774326dc492aaa8ef458c482149156a6c5add2502110000000275e3f0e9000000000000000000

1 output(s) for total of 1.536157773000 dcy

stealth address amount amount idx
00: 1fba9be744524f7450124a80f01f499bb1a1b728a2ce7cc8a838cb0613f81d5f 1.536157773000 1235096 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": 785171, "vin": [ { "gen": { "height": 785161 } } ], "vout": [ { "amount": 1536157773, "target": { "key": "1fba9be744524f7450124a80f01f499bb1a1b728a2ce7cc8a838cb0613f81d5f" } } ], "extra": [ 1, 47, 206, 56, 159, 11, 80, 57, 51, 143, 17, 80, 232, 183, 116, 50, 109, 196, 146, 170, 168, 239, 69, 140, 72, 33, 73, 21, 106, 108, 90, 221, 37, 2, 17, 0, 0, 0, 2, 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