Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b702cc52e4c2807588bb35e5057be420b2054f636f2acf3ac338c6bfc4cc583

Tx prefix hash: 13166ffd385363c5f36ebfab72d4805a6126fb40fc867dc44f3ce107e1f85199
Tx public key: 7a98e4afe105a63d72e571433dd57345f4e165ed43db657dcb7b127c5cb2d9fe
Timestamp: 1696001706 Timestamp [UCT]: 2023-09-29 15:35:06 Age [y:d:h:m:s]: 01:101:00:23:28
Block: 858804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333464 RingCT/type: yes/0
Extra: 017a98e4afe105a63d72e571433dd57345f4e165ed43db657dcb7b127c5cb2d9fe021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.875842238000 dcy

stealth address amount amount idx
00: e88455d972e7b0103ae765416618a6acc6db806f59ed29e224f5a2c656f3d8b6 0.875842238000 1313000 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": 858814, "vin": [ { "gen": { "height": 858804 } } ], "vout": [ { "amount": 875842238, "target": { "key": "e88455d972e7b0103ae765416618a6acc6db806f59ed29e224f5a2c656f3d8b6" } } ], "extra": [ 1, 122, 152, 228, 175, 225, 5, 166, 61, 114, 229, 113, 67, 61, 213, 115, 69, 244, 225, 101, 237, 67, 219, 101, 125, 203, 123, 18, 124, 92, 178, 217, 254, 2, 17, 0, 0, 0, 9, 230, 210, 127, 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