Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3069c44241fbbcd2bc749c217f68cd2e1a0883f1900b9659e6176dde8e91e0a2

Tx prefix hash: da7e420a1f3052e9db32697e36c53dcbbee21ec2746e38089a1f5d9bf8fc6cee
Tx public key: beea2ec791e1ee709538990c64cd0dc1e56a8b9f4b19cee2cef6524126973a45
Timestamp: 1728512755 Timestamp [UCT]: 2024-10-09 22:25:55 Age [y:d:h:m:s]: 00:167:01:49:29
Block: 1128124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119188 RingCT/type: yes/0
Extra: 01beea2ec791e1ee709538990c64cd0dc1e56a8b9f4b19cee2cef6524126973a4502110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e35aa6900298eb1cf877c96df56aa3ae6114f115f5b4b445b0ae9ab17046763 0.600000000000 1610941 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": 1128134, "vin": [ { "gen": { "height": 1128124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e35aa6900298eb1cf877c96df56aa3ae6114f115f5b4b445b0ae9ab17046763" } } ], "extra": [ 1, 190, 234, 46, 199, 145, 225, 238, 112, 149, 56, 153, 12, 100, 205, 13, 193, 229, 106, 139, 159, 75, 25, 206, 226, 206, 246, 82, 65, 38, 151, 58, 69, 2, 17, 0, 0, 0, 11, 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