Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ae3e26930b9e4154d5fd759355b7a4cafd8098e20f6b2908d6e8a6082241eb4

Tx prefix hash: b11e8720e1af5742bf8d62c0f00ef6a0524a76c03de8d9f6edc8daecda0bb853
Tx public key: 088bbc5d9ebed3a9b756f11a0c567ad52b582938edccb7f96ad8692befd4f27e
Timestamp: 1725185151 Timestamp [UCT]: 2024-09-01 10:05:51 Age [y:d:h:m:s]: 01:069:07:32:42
Block: 1100541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307982 RingCT/type: yes/0
Extra: 01088bbc5d9ebed3a9b756f11a0c567ad52b582938edccb7f96ad8692befd4f27e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d28aa7950a0f381d5d2d5a171e389be591edc86ebe40fdd62829d5f647d98d6 0.600000000000 1576520 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": 1100551, "vin": [ { "gen": { "height": 1100541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d28aa7950a0f381d5d2d5a171e389be591edc86ebe40fdd62829d5f647d98d6" } } ], "extra": [ 1, 8, 139, 188, 93, 158, 190, 211, 169, 183, 86, 241, 26, 12, 86, 122, 213, 43, 88, 41, 56, 237, 204, 183, 249, 106, 216, 105, 43, 239, 212, 242, 126, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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