Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f919c93c9f686d108906b63c98c6e3cc853aa171150802cf55d26a94d6a0e2

Tx prefix hash: f440905545127dceb62d540ca71f43bf2ba21fc91886f5ad3fea04333b79dcc0
Tx public key: 41c8ceda9de79622c65dadc2caabc3f9fae99035e38a9fde8dedba415cfffad8
Timestamp: 1737943650 Timestamp [UCT]: 2025-01-27 02:07:30 Age [y:d:h:m:s]: 00:142:09:21:34
Block: 1205926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101692 RingCT/type: yes/0
Extra: 0141c8ceda9de79622c65dadc2caabc3f9fae99035e38a9fde8dedba415cfffad802110000001b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14ca5f532d23b47b509a57be2b7117beab3d2dd8729521ae950d2e4c7f7c698f 0.600000000000 1692625 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": 1205936, "vin": [ { "gen": { "height": 1205926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14ca5f532d23b47b509a57be2b7117beab3d2dd8729521ae950d2e4c7f7c698f" } } ], "extra": [ 1, 65, 200, 206, 218, 157, 231, 150, 34, 198, 93, 173, 194, 202, 171, 195, 249, 250, 233, 144, 53, 227, 138, 159, 222, 141, 237, 186, 65, 92, 255, 250, 216, 2, 17, 0, 0, 0, 27, 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