Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ab30c0e465cb51a8e6ace4edbff07245a669c491656ed82edd16c945b1c5fa

Tx prefix hash: 02d798f32475ae60f609596f42a7c20f91d899310c5bca0bac2b50dd751a21fc
Tx public key: ee38df2409ed32494de29f509deb3d93a623dc0c348b88fa3732c3470c5ec771
Timestamp: 1728930852 Timestamp [UCT]: 2024-10-14 18:34:12 Age [y:d:h:m:s]: 00:101:03:51:07
Block: 1131599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72261 RingCT/type: yes/0
Extra: 01ee38df2409ed32494de29f509deb3d93a623dc0c348b88fa3732c3470c5ec77102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd241d262ec2b79cbe7bdacd4d376c806d641d4ca9b1c9a051cf88f167c4e6a2 0.600000000000 1614502 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": 1131609, "vin": [ { "gen": { "height": 1131599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd241d262ec2b79cbe7bdacd4d376c806d641d4ca9b1c9a051cf88f167c4e6a2" } } ], "extra": [ 1, 238, 56, 223, 36, 9, 237, 50, 73, 77, 226, 159, 80, 157, 235, 61, 147, 166, 35, 220, 12, 52, 139, 136, 250, 55, 50, 195, 71, 12, 94, 199, 113, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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