Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82d0a49678f9fb7a294c49241fc8d5fe2ef5f08359cb506ca74e97251ae37101

Tx prefix hash: 7d2e2cf7980254137b5ecb21e4da4654c268fa18c42093a626cdad50f997f6bd
Tx public key: b8b1e830a83bbc31c45233ab0414a75b2e788c9b041b554f699f26600c94aed1
Timestamp: 1733779663 Timestamp [UCT]: 2024-12-09 21:27:43 Age [y:d:h:m:s]: 00:031:09:51:56
Block: 1171701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22452 RingCT/type: yes/0
Extra: 01b8b1e830a83bbc31c45233ab0414a75b2e788c9b041b554f699f26600c94aed1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82cd35fea5e29e91738d18b0282ff827b3582a4f34b50239827c8d1f62f88465 0.600000000000 1657492 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": 1171711, "vin": [ { "gen": { "height": 1171701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82cd35fea5e29e91738d18b0282ff827b3582a4f34b50239827c8d1f62f88465" } } ], "extra": [ 1, 184, 177, 232, 48, 168, 59, 188, 49, 196, 82, 51, 171, 4, 20, 167, 91, 46, 120, 140, 155, 4, 27, 85, 79, 105, 159, 38, 96, 12, 148, 174, 209, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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