Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1a48aa6c9c7522ffebed324bd108d500791a854186a474520e1404b1b0ea0e

Tx prefix hash: 868bb42c264b9117da31ca0c655249257246b4e22f39eeb9a953dd5ec40403f4
Tx public key: b6c2ba098c85f487a51ad64ae359db3c9db01531f07bd268a8e3d54e2dc3aa7f
Timestamp: 1720733509 Timestamp [UCT]: 2024-07-11 21:31:49 Age [y:d:h:m:s]: 00:248:05:27:12
Block: 1063645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177330 RingCT/type: yes/0
Extra: 01b6c2ba098c85f487a51ad64ae359db3c9db01531f07bd268a8e3d54e2dc3aa7f02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9b560c4bf43a5b6fd0f4052e28e1e43ed751cec801f67e6f3f13ebb7249cfbe 0.600000000000 1534162 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": 1063655, "vin": [ { "gen": { "height": 1063645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9b560c4bf43a5b6fd0f4052e28e1e43ed751cec801f67e6f3f13ebb7249cfbe" } } ], "extra": [ 1, 182, 194, 186, 9, 140, 133, 244, 135, 165, 26, 214, 74, 227, 89, 219, 60, 157, 176, 21, 49, 240, 123, 210, 104, 168, 227, 213, 78, 45, 195, 170, 127, 2, 17, 0, 0, 0, 8, 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