Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1dc4b762b532485385d6cf201a306e701ef8c0870c00732f0235e5a66325bcc

Tx prefix hash: 28581c84ba4c21d2eb009bc8d31e1169baf99fbe53735432afaa9f117681d3e2
Tx public key: bd98f7e77da6e921b2d5d36d366da5d001ebe354cee0afb31a69ae246275c500
Timestamp: 1721008880 Timestamp [UCT]: 2024-07-15 02:01:20 Age [y:d:h:m:s]: 00:273:23:55:05
Block: 1065933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195737 RingCT/type: yes/0
Extra: 01bd98f7e77da6e921b2d5d36d366da5d001ebe354cee0afb31a69ae246275c50002110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3176ea8ea3c86a3aeb7a9e501a88a89e465ee6520e4ac17f7211beb45148bd14 0.600000000000 1536502 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": 1065943, "vin": [ { "gen": { "height": 1065933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3176ea8ea3c86a3aeb7a9e501a88a89e465ee6520e4ac17f7211beb45148bd14" } } ], "extra": [ 1, 189, 152, 247, 231, 125, 166, 233, 33, 178, 213, 211, 109, 54, 109, 165, 208, 1, 235, 227, 84, 206, 224, 175, 179, 26, 105, 174, 36, 98, 117, 197, 0, 2, 17, 0, 0, 0, 12, 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