Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48f42560a99a98b1e46e5d8db226534143fd49946dd0f166f201b4e183e4e59

Tx prefix hash: 06bfe49c2eb7be650235ae9fd8067fe85b5acae68abc976b5b5a73e19e3cc7b0
Tx public key: 339e7c6d66287fd86efb2be710f9572dd005a55cee7f860b3329cd5328f2965a
Timestamp: 1709852678 Timestamp [UCT]: 2024-03-07 23:04:38 Age [y:d:h:m:s]: 01:061:15:38:30
Block: 973441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305071 RingCT/type: yes/0
Extra: 01339e7c6d66287fd86efb2be710f9572dd005a55cee7f860b3329cd5328f2965a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0b6521ec1d3256851f71f8ca8365bc6413662d0bbf10c1ef1f64bdebc4a1d55 0.600000000000 1433376 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": 973451, "vin": [ { "gen": { "height": 973441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0b6521ec1d3256851f71f8ca8365bc6413662d0bbf10c1ef1f64bdebc4a1d55" } } ], "extra": [ 1, 51, 158, 124, 109, 102, 40, 127, 216, 110, 251, 43, 231, 16, 249, 87, 45, 208, 5, 165, 92, 238, 127, 134, 11, 51, 41, 205, 83, 40, 242, 150, 90, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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