Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233acf251a7ab8762a1fcf8375d4c7cbac594dca9ab992f2a95d27bbd3580349

Tx prefix hash: 724f8f954599b3396e5e4e9eb0ecb297a00311516b3c2e64c732cdf4e7d72f6b
Tx public key: b0f89de353c0a0a8982d8d9ac6290a0ee5fdd8311881dc4f6d851c9a8a298cfa
Timestamp: 1657106798 Timestamp [UCT]: 2022-07-06 11:26:38 Age [y:d:h:m:s]: 02:258:04:49:50
Block: 537834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705698 RingCT/type: yes/0
Extra: 01b0f89de353c0a0a8982d8d9ac6290a0ee5fdd8311881dc4f6d851c9a8a298cfa0211000000014da16a3a000000000000000000

1 output(s) for total of 10.137546110000 dcy

stealth address amount amount idx
00: 3f858aa51a3c6dfd9b50e72ca24a89b8a526ede303edc8bed302cca23ccac8ba 10.137546110000 967765 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": 537844, "vin": [ { "gen": { "height": 537834 } } ], "vout": [ { "amount": 10137546110, "target": { "key": "3f858aa51a3c6dfd9b50e72ca24a89b8a526ede303edc8bed302cca23ccac8ba" } } ], "extra": [ 1, 176, 248, 157, 227, 83, 192, 160, 168, 152, 45, 141, 154, 198, 41, 10, 14, 229, 253, 216, 49, 24, 129, 220, 79, 109, 133, 28, 154, 138, 41, 140, 250, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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