Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbed8e56bf06eea93467b038964029b06da6a164a57579a9db4dc9a9d5182cd5

Tx prefix hash: 3f612134341da44dd3600ea4b01f8febd688c2f1a26a3df6ecae2978c320adbe
Tx public key: f25f9940e941af7e0ce7e3b2984c3f62bc82da7af32e42dcf1f6efb7759d7756
Timestamp: 1733047606 Timestamp [UCT]: 2024-12-01 10:06:46 Age [y:d:h:m:s]: 00:113:12:51:10
Block: 1165634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80929 RingCT/type: yes/0
Extra: 01f25f9940e941af7e0ce7e3b2984c3f62bc82da7af32e42dcf1f6efb7759d7756021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 320c68f27c4c850617caca75da65669336bd64b0f95a540f991203e0a3b46fa0 0.600000000000 1651309 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": 1165644, "vin": [ { "gen": { "height": 1165634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "320c68f27c4c850617caca75da65669336bd64b0f95a540f991203e0a3b46fa0" } } ], "extra": [ 1, 242, 95, 153, 64, 233, 65, 175, 126, 12, 231, 227, 178, 152, 76, 63, 98, 188, 130, 218, 122, 243, 46, 66, 220, 241, 246, 239, 183, 117, 157, 119, 86, 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