Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898c7a23503866480b2ce76b7b6ecba4b7008ee11a874236f10f55ed89a3fa01

Tx prefix hash: e6933c6eb9b15025742c22f0d2c928cd6cc5d9b99ab064ef5a4863d50939587a
Tx public key: 27abfde1589737ea2fa89517796e4ee1754f6f12426d9e9914a93911a0f72eda
Timestamp: 1687100142 Timestamp [UCT]: 2023-06-18 14:55:42 Age [y:d:h:m:s]: 01:317:15:18:11
Block: 785057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488180 RingCT/type: yes/0
Extra: 0127abfde1589737ea2fa89517796e4ee1754f6f12426d9e9914a93911a0f72eda021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.537377137000 dcy

stealth address amount amount idx
00: 60264fb28ba4f76bab9a5224d928d8ebc596e5e920eaea6303272b5e18a9931d 1.537377137000 1234980 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": 785067, "vin": [ { "gen": { "height": 785057 } } ], "vout": [ { "amount": 1537377137, "target": { "key": "60264fb28ba4f76bab9a5224d928d8ebc596e5e920eaea6303272b5e18a9931d" } } ], "extra": [ 1, 39, 171, 253, 225, 88, 151, 55, 234, 47, 168, 149, 23, 121, 110, 78, 225, 117, 79, 111, 18, 66, 109, 158, 153, 20, 169, 57, 17, 160, 247, 46, 218, 2, 17, 0, 0, 0, 3, 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