Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc850638c3ed89f424e0ca28a006e1b3d68f378593f6696af2ac0fe9c57d9c2

Tx prefix hash: 767ec1b29d0ffe10911876f7e284d1b994968ddc6e0728e7ce6ab28d966c78aa
Tx public key: 2c8caf44e5f8f26799a143a18b79220b2d9d425d80ac4450eeffabcee4d5df26
Timestamp: 1730617953 Timestamp [UCT]: 2024-11-03 07:12:33 Age [y:d:h:m:s]: 00:143:03:42:17
Block: 1145496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102125 RingCT/type: yes/0
Extra: 012c8caf44e5f8f26799a143a18b79220b2d9d425d80ac4450eeffabcee4d5df260211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fc6585dc8aee9cc706fee478aa19fc2bf116b4afef467e0889514b3c37a9115 0.600000000000 1629939 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": 1145506, "vin": [ { "gen": { "height": 1145496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fc6585dc8aee9cc706fee478aa19fc2bf116b4afef467e0889514b3c37a9115" } } ], "extra": [ 1, 44, 140, 175, 68, 229, 248, 242, 103, 153, 161, 67, 161, 139, 121, 34, 11, 45, 157, 66, 93, 128, 172, 68, 80, 238, 255, 171, 206, 228, 213, 223, 38, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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