Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4db24812f9ab8441a74d5562e93ac93b78d57e9691ca83c6ebcfd86f03002a5

Tx prefix hash: b2c1935187e0e4e7713f7264d93bd130cd53e4b986d281ce8aca5a5abaecd2f1
Tx public key: d77886d5ddadc1f8560e6d5fef3a77c9b10a0b44d35a8db82933c925c6b241af
Timestamp: 1704729954 Timestamp [UCT]: 2024-01-08 16:05:54 Age [y:d:h:m:s]: 01:067:07:12:26
Block: 930950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309223 RingCT/type: yes/0
Extra: 01d77886d5ddadc1f8560e6d5fef3a77c9b10a0b44d35a8db82933c925c6b241af02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c172308f575928a95cce9876e6e0c5f699c5d7e745b897e528ec9bb4acc14bc4 0.600000000000 1388840 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": 930960, "vin": [ { "gen": { "height": 930950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c172308f575928a95cce9876e6e0c5f699c5d7e745b897e528ec9bb4acc14bc4" } } ], "extra": [ 1, 215, 120, 134, 213, 221, 173, 193, 248, 86, 14, 109, 95, 239, 58, 119, 201, 177, 10, 11, 68, 211, 90, 141, 184, 41, 51, 201, 37, 198, 178, 65, 175, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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