Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b803317584da4ced042ce497e62f78aa12f0493240cef9c213f2a098f04044e2

Tx prefix hash: d0913aca507c18ed6c9d7a28f4bcaa9d64209a5b0bcdfc20d5e140a13ab64721
Tx public key: d32e9ffd176bb665bc8f194e5de9fccca6c03d18b4cf0967277c8681e128f9fd
Timestamp: 1702875522 Timestamp [UCT]: 2023-12-18 04:58:42 Age [y:d:h:m:s]: 01:152:20:42:17
Block: 915588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370399 RingCT/type: yes/0
Extra: 01d32e9ffd176bb665bc8f194e5de9fccca6c03d18b4cf0967277c8681e128f9fd02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e221559a99d01d6ba3712c62772c4c7e93a73d413c38b7e6b0488f78d11c875e 0.600000000000 1372984 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": 915598, "vin": [ { "gen": { "height": 915588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e221559a99d01d6ba3712c62772c4c7e93a73d413c38b7e6b0488f78d11c875e" } } ], "extra": [ 1, 211, 46, 159, 253, 23, 107, 182, 101, 188, 143, 25, 78, 93, 233, 252, 204, 166, 192, 61, 24, 180, 207, 9, 103, 39, 124, 134, 129, 225, 40, 249, 253, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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