Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3496a67700bff0ac6003578227e3c4fdc897cfbb50c365afb4128e2a3c58705

Tx prefix hash: fafdc5c38c9b54489b7e8e90734a75ec8951d787e75c2d5d77a1d27f138795d5
Tx public key: e652cde32ca27a76372f689c0ed458ed5c26ff1a58d0b3606f0f93dcfbd1a682
Timestamp: 1710680511 Timestamp [UCT]: 2024-03-17 13:01:51 Age [y:d:h:m:s]: 00:187:17:26:46
Block: 980310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134455 RingCT/type: yes/0
Extra: 01e652cde32ca27a76372f689c0ed458ed5c26ff1a58d0b3606f0f93dcfbd1a6820211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebb2b85cc2007d36282acd4a0ff5221765f12d72cb7b1502d86a9f4bfc41ca2e 0.600000000000 1440375 of 15

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": 980320, "vin": [ { "gen": { "height": 980310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebb2b85cc2007d36282acd4a0ff5221765f12d72cb7b1502d86a9f4bfc41ca2e" } } ], "extra": [ 1, 230, 82, 205, 227, 44, 162, 122, 118, 55, 47, 104, 156, 14, 212, 88, 237, 92, 38, 255, 26, 88, 208, 179, 96, 111, 15, 147, 220, 251, 209, 166, 130, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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