Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f931fbbe54a51556eb6e42348c44389cde1ab5656789068008bddf505ccd920c

Tx prefix hash: 73eff40885d7b4bc5c4f9f8c8ad6634653758298160b2a79f870d818e589431a
Tx public key: f66cc7d02538f1b0db29827e8f1cb9cb2ea6930972fa610f6ba52a09bf10e0ac
Timestamp: 1716733040 Timestamp [UCT]: 2024-05-26 14:17:20 Age [y:d:h:m:s]: 00:297:09:20:02
Block: 1030483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212554 RingCT/type: yes/0
Extra: 01f66cc7d02538f1b0db29827e8f1cb9cb2ea6930972fa610f6ba52a09bf10e0ac02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef0c4648c61ca98ae1ab1ba8c7885d29c0e314ed54782ea0a32533b7d60c4a63 0.600000000000 1498738 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": 1030493, "vin": [ { "gen": { "height": 1030483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef0c4648c61ca98ae1ab1ba8c7885d29c0e314ed54782ea0a32533b7d60c4a63" } } ], "extra": [ 1, 246, 108, 199, 208, 37, 56, 241, 176, 219, 41, 130, 126, 143, 28, 185, 203, 46, 166, 147, 9, 114, 250, 97, 15, 107, 165, 42, 9, 191, 16, 224, 172, 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