Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1568b082e86b842eee951184ac35e09cd984213e08b61438e2f82e280d41176

Tx prefix hash: 5eb557a99652d904fd2057c06210a51207d41df6ea7c692e4a2c2a895ee61ac0
Tx public key: 09537829fb2f2de5295d87093fd92f60a9d7d85ca03aa42909487d2bcff3f466
Timestamp: 1714201184 Timestamp [UCT]: 2024-04-27 06:59:44 Age [y:d:h:m:s]: 00:322:13:56:58
Block: 1009474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230612 RingCT/type: yes/0
Extra: 0109537829fb2f2de5295d87093fd92f60a9d7d85ca03aa42909487d2bcff3f4660211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 432e8e7b2e38f54e8d25f01503e4988a85716e503b14dbb13bdebd9e72b890bc 0.600000000000 1471156 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": 1009484, "vin": [ { "gen": { "height": 1009474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "432e8e7b2e38f54e8d25f01503e4988a85716e503b14dbb13bdebd9e72b890bc" } } ], "extra": [ 1, 9, 83, 120, 41, 251, 47, 45, 229, 41, 93, 135, 9, 63, 217, 47, 96, 169, 215, 216, 92, 160, 58, 164, 41, 9, 72, 125, 43, 207, 243, 244, 102, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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